Bolero is the premier Web logging analysis and reporting system for the Macintosh. With Bolero you’ll unearth the activity and user demographics that can justify a Web site’s investment. Bolero shows not only how many visitors are using a site, but where they are coming from, what attracted them, and what they are doing once they arrive.
Bolero's list of features include:
• Real-time logging
• Logging of single or multiple Web servers simultaneously
• Post processing of historical data (WebSTAR *.log files)
• Open Database Connectivity (ODBC) support
• User-customizable filtering of incoming data
• Data is stored in an industry-standard SQL database, giving you unsurpassed
flexibility in reporting
Installing Bolero
Bolero installation is a three step process. Please consult the Bolero Administrator’s Guide for detailed instructions. During this procedure you will…
1) Install Bolero, which logs your web server(s)
2) Install Butler SQL, which stores the data received by Bolero
3) Install Tango, which enables you to access the Bolero reports via your web server
The Butler SQL server in this package is a fat application, which means that it has been optimized for both 680x0 Macintosh and Power Macintosh computers.
The Tango.acgi application in this package are provided in both 68K and Power Macintosh native formats.
All documentation included with Butler SQL and Bolero is in Adobe Acrobat (.pdf) format. If you do not already have Adobe Acrobat installed on your computer, an Acrobat Reader Installer is included with this package.
What Gets Installed
When installing Bolero, the Easy Install option installs the following components onto your computer:
• Bolero, BoleroImporter and supporting files
• Apple Shared Library Manager 2.0, if not already present
• ODBC 2.1, if not already present
• Butler SQL 68K ODBC Driver
When installing Butler SQL, the Easy Install option installs the following components onto your computer:
• Butler SQL server and client applications
• An empty BoleroDatabase
• Default Tables configuration file (refer to the Default Tables section later in this document)
When installing Tango, the Easy Install option installs the following components onto your computer:
• Tango.acgi
• ButlerLink Access extension
• The Bolero ‘Web’ environment, with online documentation and reports
_____________________________________________
Thank you for purchasing Bolero. If you have any questions or suggestions, please feel free to email our technical support department at <support@everyware.com>
EveryWare Development Corp.
6733 Mississauga Road, 7th Floor
Mississauga, Ontario
Canada L5N 6J5
tel: (905) 819-1173
fax: (905) 819-1172
www: http://www.everyware.com/
_____________________________________________
Bolero 1.0.3 Release Notes
There have been some last minute modifications to Bolero that are not reflected in the Administrator’s Guide.
New Features and Fixes:
•1) Added the ability to support RAIC (Redundant Arrays of Inexpensive Computers) configurations for
Web Servers. Make the following change in your 'Bolero Settings' file if you need this option.
[www.myserver1.com]
DomainName = www.myserver1.com
IPAddress = 255.255.255.255
Type = WebSTAR
Zone = ServerLand
Machine = My Server 1
Program = WebSTAR 1.2.5
Timeout = 300
GroupName = AliasServer
Where AliasServer could be any name of length less than or equal to 31 characters. You can group as many Web Servers as you want by assigning the same group name to each Web Server definition. You can have grouped and ungrouped Web Server definitions in the same settings file. This parameter is optional and can be deleted. It is needed only in case you want to log multiple Web Servers as one entity in the database and the name of it will be the name you give your group.
•2) BoleroImporter is no longer counted as an additional web server for Bronze serial numbered Boleros.
•3) A Test Drive capability was added (limited to 25,000 entries in a Bolero Database).
BoleroDatabase: ‘Byte’ data stored as ‘Kilobytes’
With the exception of the ActivityLog table, all references in the Bolero Administrator’s Guide to the BytesSent, BytesSentToDate, percentBytesSent and averageBytesSent should be referred to as KBytesSent, KBytesSentToDate, percentKBytesSent and averageKBytesSent. Data is stored as kilobytes in these columns, with decimal precision.
Bolero Settings File: [GeneralSettings]
A new user-configurable option has been added to the Bolero Settings file:
[GeneralSettings]
Summaries=On
The ability to disable summary execution completely (Summaries=Off) is very useful, for example, when simultaneously logging a ‘live’ web server and also importing several log files from previous weeks or months. Temporarily disabling summary execution will prevent Bolero from unwantingly executing the same summary, or summaries, repeatedly.
Butler SQL: Default Tables
Included with the Bolero package is a file, ‘Default Tables’ which is placed in the root level of the ‘Butler Preferences Folder’ on the Butler SQL server.
Default Tables will improve insert, update and delete times. Following is an excerpt from Butler Tech Note #28:
The “Default Tables” file is a text file in the ‘Butler Preferences Folder’ with each line representing a different table. The format of every line of the default table file is “database!tablename” [no quotes] and may have other parameters added after the tablename with comma delimiters. These will include a keyword “NOCACHE” or “CACHE”. If the keyword doesn’t exist, it defaults to “NOCACHE” (see the follow section on how caching works). This feature is an APPLICATION level setting and will therefore affect all users.
SYNTAX:
databaseName!tableName ,[cache|noCache]
eg:
dal_demo!customer, cache
dal_demo!orders, noCache
dal_demo!staff
There are two main benefits to be gained by this feature:
A) reduce the number of table open journal entries to reduce journal size;
B) increase OPEN TABLE speeds.
Tables opened in this manner will NOT be defined as OPEN, just prepared for open. That is, while Butler has opened the tables and logged the open into the Butler journal for transaction processing, they are not usable nor displayed by Butler as “open” until implicitly opened using some DML or explicitly opened with an OPEN TABLE statement. Therefore, DDL statements like ALTER, DROP and CREATE should be unaffected by this feature. BACKUP should also be unaffected by these prepared tables. COMPACT represents a problem because Butler expects all Butler table references to be closed prior to the compact.
Two runtime commands have been implemented to allow manipulation of the DEFAULT TABLES set after server launch. One to unload all default tables, one to reload default tables. There are two times when default tables will be defined, once at boot and whenever the 'load' runtime is submitted by any user. There are two times when default tables will be purged: one at program termination and whenever the unload runtime is submitted by any user.
The runtimes to load or unload the default tables are:
$setruntime(loaddefaulttables, true); /* loads the default tables */
$setruntime(loaddefaulttables, false); /* unloads the default tables */
